Mobile safety platform

ABSTRACT

A system for monitoring a safety condition of a user includes a hero device associated with a hero, and a mobile device associated with the user. The mobile device comprises a processor and a memory device, the memory device configured to store a safety mobile application enabling the mobile device to: receive, from the user, an indication of an emergency situation, record a video of the user in the emergency situation, determine a geolocation of the mobile device, and communicate to the hero device a message comprising the video of the user in the emergency situation and the geolocation of the mobile device. The recording of the video, the determining of the geolocation, and the communicating of the message are automatically activated in succession following the indication of the emergency situation by the user.

REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.14/984,693, filed Dec. 30, 2015, which claims the benefit of U.S.Provisional Application No. 62/099,226, filed Jan. 2, 2015, which arehereby specifically incorporated by reference in its entirety.

TECHNICAL FIELD

This disclosure relates to mobile application systems. Morespecifically, this disclosure relates to mobile application systemshaving a safety platform.

BACKGROUND

In general, this disclosure relates to techniques to provide a safetymobile application to enable a user to monitor and record safety relatedinformation and facilitate communication of this safety relatedinformation between the user and another party.

SUMMARY

Disclosed is a system for monitoring a safety condition of a user, thesystem including: a hero device; a measuring device; and a mobiledevice, the mobile device including a processor and a memory device, thememory device configured to store a safety mobile application enablingthe mobile device to: record a video recording of the user using themeasuring device during a measuring period, receive, from the measuringdevice, user data measured by the measuring device of the user duringthe measuring period, transmit, to a server, the user data and videorecording of the user from the measuring period, and transmit, to thehero device, a status report message including the user data and videorecording of the user from the measuring period.

Also disclosed is a system for monitoring a safety condition of a user,the system including: a hero device; and a mobile device associated withthe user, the mobile device including a processor and a memory device,the memory device configured to store a safety mobile applicationenabling the mobile device to: receive, from the user, an indication ofan emergency situation, record a video of the user in the emergencysituation, determine a geolocation of the mobile device, and communicateto the hero device a message including the video of the user in theemergency situation and the geolocation of the mobile device

Also disclosed is a method of monitoring a safety condition of a user,the method including: receiving from the user an indication of anemergency situation; recording a video of the user in the emergencysituation; determining a geolocation of a mobile device associated withthe user; and communicating a message to a hero device, the messageincluding the video of the user in the emergency situation and thegeolocation of the mobile device.

Various implementations and examples described in the present disclosuremay include additional systems, methods, features, and advantages, whichmay not necessarily be expressly disclosed herein but will be apparentto one of ordinary skill in the art upon examination of the followingdetailed description and accompanying drawings. It is intended that allsuch systems, methods, features, and advantages be included within thepresent disclosure and protected by the accompanying claims. It shouldbe appreciated that the disclosed safety mobile application andassociated techniques including methods, systems, devices, and variousapparatuses is described in several examples among many. No particularterminology or description should be considered limiting on thedisclosure or the scope of any claims issuing therefrom.

BRIEF DESCRIPTION OF THE DRAWINGS

The features and components of the following figures are illustrated toemphasize the general principles of the present disclosure.Corresponding features and components throughout the figures may bedesignated by matching reference characters for the sake of consistencyand clarity.

FIG. 1A illustrates one example of a system employed for implementing asafety mobile application according to an example of the presentdisclosure.

FIG. 1B illustrates another examples of a system employed forimplementing a safety mobile application according to an example of thepresent disclosure.

FIGS. 2-19 illustrate example user interface screenshots according toexample embodiments of the present disclosure.

FIG. 20 illustrates an example of a method of for monitoring a safetycondition of a user with a safety mobile application according to thepresent disclosure.

FIG. 21 illustrates another example of a method for monitoring a safetycondition of a user with a safety mobile application according to thepresent disclosure.

DETAILED DESCRIPTION

The following description is presented to enable one skilled in the artto make and use the elements of the disclosure and is provided in thecontext of particular applications and their requirements. Thus, thefollowing description of examples consistent with the present disclosureprovides illustration and description but is not intended to beexhaustive or limiting to the precise form disclosed. Variousmodifications to the disclosed examples will be apparent to thoseskilled in the art, and the general principles set forth below may beapplied to other examples and applications. For example, although aseries of acts, features, or elements may be described with reference toa flow diagram, the order of such acts, features, or elements may differin other implementations when the performance of one act is notdependent on the completion of another act. Further, non-dependent actsmay be performed in parallel. No element, act or instruction used in thedescription should be construed as critical or essential to any exampledisclosed herein unless explicitly described as such. Also, as usedherein, the article “a” is intended to include one or more items. Whereonly one item is intended, the term “one” or similar language is used.Thus, the present disclosure is not intended to be limited to theexamples illustrated and described.

FIG. 1A illustrates a simplified communication system 100 a for thereceiving, storing, transmitting, and utilization of a safety conditionof a user 112. Not all of the depicted components may be required,however, and some systems may include additional, different, or fewercomponents not illustrated in the figures. Variations in the arrangementand the type of components may be made without departing from the spiritor scope of the claims as set forth herein.

As illustrated in FIG. 1A, in various examples, the system 100 aincludes a user device 102 and a safety server 104. In various examples,the system 100 a includes a hero device 106, which is a third partydevice. The system 100 a may also include service providers 110 a,b,c.The number of hero devices 106 or service providers 110 should not beconsidered limiting on the current disclosure. In various examples, theuser device 102 and hero 106 are mobile devices including anyappropriate type of computing system and/or computing device, including,but not limited to, a mobile phone, a tablet, a laptop, a smartphone, afeature phone, a personal digital assistant, a media player, anelectronic book reader, a wearable computing device, a smart display, orany other similar device. As illustrated in FIG. 1A, in various examplesthe user device 102 is communicatively coupled with the safety server104, the hero 106, and the service providers 110 a,b,c via a network108. The network 108 may be the Internet, a Wide Area Network (WAN), aLocal Area Network (LAN), a Wireless Local Area Network (WLAN), or anyother similar type of network or combination thereof. As used herein,the phrase “coupled with” includes communications where two devices aredirectly connected to or indirectly connected through one or moreintermediate components. Such intermediate components may include bothhardware, software, or network based components. Variations in thearrangement and the type of components may be made without departingfrom the spirit or scope of the claims as set forth herein.

The user device 102 is operable to be used by a user 112. As illustratedin FIG. 1A, in various examples, the user device 102 includes aprocessor 140 and a memory 150. The user device 102 may also includenetwork and input/output (I/O) interfaces 142, a user interface 144, andstorage 146. In various examples, the processor 140 of the user device102 accesses the safety server 104 through wireless or wiredcommunication. In various examples, the processor 140 executes aspecific set of program instructions of a safety application stored inthe memory 150 such that the user device 102 may display information,receive user input, receive image and/or video data, to receive andtransmit data to the safety server 104, hero 106, or service providers110 via the network 108, and otherwise enable the user 112 to interactwith the user device 102 as described in greater detail below. If theuser device 102 does not have such program instructions available, thenthe user 112 may install such program instructions.

In various examples, the user interface 144 is a screen or display thatenables the user 112 to interact with the user device 102. The userinterface 144 may include at least touch screens, device buttons,keypads, stylus, or other similar devices for inputting information andinteracting with the user device 102. As described below with referenceto FIG. 2, in various examples, the user interface 144 enables the user112 to enter the user's identification, input contact information for ahero 114, select existing contact information for a hero 114, selectvarious other third party contact information, select various selectablebuttons or icons presented on the user interface 144, and performvarious other interactions with the user device 102. As used herein, thehero 114 is a contact designated by the user 112 to receive the safetyinformation described herein. The hero 114 may be family members,relatives, friends, designated drivers, employers, probation officers,campus security, or any other contact designated by the user 112 toreceive the safety information.

In various examples, the memory 150 of the user device 102 is acomputer-readable medium, such as a non-transitory computer-readablestorage medium, that stores instructions executable by the processor.Thus, the memory 150 may be, for example, random access memory (RAM),electrically-erasable programmable read-only memory (EPPROM), a storagedrive, an optical disk, and any other suitable type of volatile ornon-volatile memory that stores instructions to cause a programmableprocessor (i.e., processing resource) to perform the techniquesdescribed herein. In examples, the memory 150 includes a main memory,such as a RAM in which the instructions may be stored during runtime,and a secondary memory, such as a nonvolatile memory in which a copy ofthe instructions is stored. The memory 150 is non-transitory in thesense that it does not encompass a transitory signal but instead is madeup of one or more memory components configured to store the instructionsdescribed in greater detail below. The memory 150 may be representativeof a memory resource and may store machine executable instructions,which are executable on a computing system such as the user device 102in conjunction with processor 140. The memory 150 may also include oneor more data structures for storing information. The computer executableprogram code or instructions in this scenario, may include one or moreapplication programs, other program modules, program data, firmware,and/or an operating system 152. In various examples, the safety mobileapplication includes a BAC monitoring module 154 and an emergency module156 stored in the memory 150. In various examples, the safety mobileapplication includes two modules: an emergency module 156 and a BloodAlcohol Content (BAC) monitoring module. An example of a routine ormethod performed by the BAC monitoring module 154 is illustrated in FIG.20. An example of a routine or method performed by the emergency module156 is illustrated in FIG. 21. In various examples, the hero 106 issimilar to the user device 102 and includes a processor, memory, anduser interface.

As illustrated in FIG. 1A, the system 100 a includes the safety server104. In various other examples, the system 100 a may include acombination of different servers accomplishing the functions attributedto the safety server 104. In various examples, the safety server 104includes one or more memories, one or more processors or controllers,and one or more data structures. The memory is a computer-readablemedium that stores instructions to be performed by the safety server104. The safety server 104 may be a centralized server of cluster ofserver computers that maintains the processes and data structures for anumber of different users, or it may represent a distributed set ofcomputers located in different geographic regions, each computer servinga different group of users, or it may be any other equivalent orcombination thereof. The processor is used to access data from and storedata in the data structures and to communicate with devices outside ofthe safety server 104. In various examples, the safety server 104includes the data structures; however, in various other examples, thedata structures is external to and accessible by the safety server 104,such as via the network 108 or other communication technique. In variousexamples, the data structures includes data corresponding to registeredusers. The data structures are created by entering in various types ofdata from a user 112 (or a number of various different users). This datamay include user identification information such as name, address,telephone number, height, weight, gender, email address, Short MessageService (SMS)/Multimedia Messaging Service (MMS) address, and any othersuitable information capable of identifying a specific registered user112. The stored data may also include user history information, resultshistory, video, pictures, notes, text, rules (e.g. blood alcohol content(BAC) levels, Panic levels, Parent based rules, etc.), health relateddata, and various other types of data corresponding to specific users.

In various examples, the user device 102 may access the data on thesafety server 104. In various examples, the data is encrypted on thesafety server 104 as a security feature of the system 100 a. In variousexamples, additional security features such as password protection areutilized to secure and limit access to the data. Storage on the safetyserver 104 provides privacy by maintaining this data in accordance withpayment-card industry (PCI), personally-identifiable information (PII),and/or other standards concerning data capture and privacy. In variousexamples, the user data may require user verification such as throughpassword, fingerprint scan, photo verification, or various other typesof user verification if the user 112 desires to remove a user datahistory created by the safety mobile application

In various examples, other databases, including non-proprietarydatabases, of various service providers 110 may be utilized to provideinformation to the user device 102. In various examples, these databasesinclude those databases associated with various social media platforms(e.g. Facebook®, LinkedIn®, Google+®, etc.). In various examples, theuser device 102 may access various social media platforms via anApplications Programming Interface (API), a web-based interface, orvarious other equivalents or combinations thereof. The service providers110 include a centralized server or cluster of server computers. Theservice providers include includes one or more memories, one or moreprocessors or controllers, and one or more data structures. The memoryis a computer-readable medium that stores instructions to be performedby the service providers 110. The processor is used to access data fromand store data in the data structures and to communicate with devicesoutside of the service providers 110.

In various examples, the user device 102 is able to communicate with thevarious service providers 110 via the network 108. The service providers110 may be able to provide any sort of service to its end users. Forexample, the service providers 110 may be a taxi service, adriver-for-hire service, a hotel or hotel-finder service, a designateddriver service, a lawyer-referral service, a legal assistance service, acar-rental service, a health promotion service, a rehabilitationservice, a health safety service, or various other types of services. Invarious examples, the user device 102 running the safety application maycommunicate with the service providers 110 via an API or web-basedinterface.

In various examples, the user device 102 is also in communication with ameasuring device 120. In various examples, the measuring device 120 is abreathalyzer alcohol sensor; however, the disclosure of a breathalyzeras a measuring device 120 should not be considered limiting on thecurrent disclosure. Other appropriate types of devices and/or sensorsmay be used in place of the breathalyzer, including, but not limited to,a heart rate monitor (e.g. those incorporated into wearable technologylike Fitbit, Apple Watch, Android Watch, and various other similardevices), activity trackers, and various other measuring devices. In theexamples where the measuring device 120 is a breathalyzer, the measuringdevice 120 contains the requisite components to detect and record a BACof a breath of the user 112. The measuring device 120 then transmits theBAC data to the user device 102. In various examples, the measuringdevice 120 is in wired and/or wireless communication with the userdevice 102. In various examples, the measuring device 120 is in wirelesscommunication with the user device 102 utilizing Bluetooth, wirelessEthernet, and/or near field communication technology. The number ofmeasuring devices 120 should not be considered limiting on the currentdisclosure.

In various examples, the user device 102 is in communication withvarious other devices such as a car ignition interlock. In variousexamples, the user device 102 is in communication with the car ignitioninterlock via Bluetooth or using another suitable wired or wirelesstechnology. The user device 102 running the safety mobile applicationmay be able to prevent the user 112 from starting a car via the carignition interlock if certain parameters are met, as described ingreater detail below.

The number of servers, processors, memory, databases, and userinterfaces should not be considered limiting on the current disclosure.Furthermore, the configuration illustrated in FIG. 1A for the userdevice 102, hero 106, and safety server 104 is for illustrative purposesonly and should not be considered limiting on the current disclosure. Invarious examples, the safety mobile application described herein iscompliant with certain mobile device operating systems (OSs), such asApple's iOS, Google's Android, and various other operating systems.

FIG. 1B illustrates another example of a simplified communication system100 b for the receiving, storing, transmitting, and utilization of asafety condition of the user 112. Similar to the system 100 a, thesystem 100 b includes the user device 102, the safety server 104, thehero 106, and the service providers 110 a,b,c. As illustrated in FIG.1B, in various examples, the user device 102 is in communication with afirst measuring device 120 a and a second measuring device 120 b. Eachmeasuring device 120 a,b may measure a different type of user dataduring a measuring period. For example, a first measuring device maymeasure a first type of user data during the measuring period and asecond measuring device may measure a second type of user data duringthe measuring period. In various examples, the first measuring device120 a is a breathalyzer configured to measure the BAC of a user 112 andthe second measuring device 120 b is a heart rate monitor configured tomeasure a heart rate of the user 112. However, the number of measuringdevices 120 and type of measuring devices 120 should not be consideredlimiting on the current disclosure as in various other examples, anydesired number of measuring devices 120 may be utilized.

FIGS. 2 and 3 illustrate examples of user interfaces 200,300 on the userdevice 102 operated by the user 112. It should be noted that the labelsand placement of interface elements are representative only and that theimportance is on their underlying functions. Likewise, it should beunderstood that any buttons can be physically moveable switches,softkeys, proximity switches, voice detectors, motion sensor, etc.operable to perform a function in response to user's 112 desires.

In FIG. 2, the user 112 may engage with a login element 202 afterlaunching the safety mobile application on the user device 102 for thefirst time. The safety mobile application may utilize the login element202 to provide access control to the safety mobile application invarious examples. In various examples, the user 112 may login usingsocial media account credentials such as a social media username andpassword with Facebook®, LinkedIn®, Google+®, or various other similaraccounts. In various examples, the safety mobile application may alsoprovide options to the user 112 to create an account. The user 112 maycreate an account by providing personal credentials and a password fromscratch or log in to another existing account not associated with asocial media platform. If a user 112 logs in with social media oranother account, the safety mobile application may import the user's 112name, email, or other identifying personal credentials.

The user-entered username and password are transmitted to the safetyserver 104 to create a new user account or to authenticate against anexisting user account. In various examples, after the user 112 has beenauthenticated, the user 112 may remain logged in such that subsequentlaunches of the safety mobile application may not require the user 112to reenter the user's 112 username and password. In various otherexamples, the user 112 may be logged out of the safety mobileapplication after exiting the safety mobile application.

FIG. 2 illustrates the user interface 200 in accordance with aspects ofthe present disclosure. In particular, the user interface 200 may beused by the user 112 to engage with the hero designation element 204.Engagement with the hero designation element 204 causes a hero 114 to bedesignated by the user 112. The selection of the hero 114 via the herodesignation element 204 is transmitted to and stored by the safetyserver 104. As previously described, a hero 114 is a contact designatedby the user 112 to receive the safety information described herein. Invarious examples, the hero 114 is selectable from a list of contactswith contact information stored in the memory of the user device 102. Invarious examples, the hero 114 and associated contact information may beentered by the user 112. The contact information may include informationfrom the group including, but not limited to, name, address, telephonenumber, social media address, SMS/MMS number, email address, or anyother contact information.

As illustrated in FIG. 2, in various examples, the user 112 may alsoengage an agreement element 206. The agreement element 206 may includethe safety mobile application's Terms of Use and Privacy Policy invarious examples. The Terms of Use may clarify that the safety mobileapplication is an application for reference purposes only and does notactually prevent dangerous situations from occurring. For example, invarious examples, the Terms of Use clarify that the safety mobileapplication does not actually prevent dangerous situations such asimpaired driving or domestic violence. For example, in various examples,the Terms of Use may further clarify that the user 112 is agreeing touse the safety mobile application at his or her own risk. In variousexamples, the Privacy Policy may indicate how data collected by themobile application will be used, where the data will be stored, and whoowns the data in various examples. For example, in various examples, anydata collected by the safety mobile application is stored on the safetyserver 104. This data may be fully encrypted in various examples. Invarious examples, the user 112 owns the data stored on the safety server104 and has the right to determine whom they share the data with invarious examples. In various examples, the data stored on the safetyserver 104 is further password protected to further secure and limitaccess to the stored data on the safety server 104.

FIG. 3 illustrates the user interface 300 in accordance with aspects ofthe present disclosure. In particular, the user interface 300 may beused by the user 112 upon successful log in to the safety mobileapplication and/or successful launch of the safety mobile application.In various examples, after the user 112 has logged in to the safetymobile application, the safety mobile application is configured to timeand date stamp the beginning and end of the various activities performedby the user 112 described herein. The safety mobile application may alsobe configured to provide location information for the various activitiesperformed by the user 112. As previously described, this data istransmitted to the safety server 104 for secure storage.

As illustrated in FIG. 3, the user 112 may engage with a panic element308, which will be described in greater detail below. Engagement withthe panic element 308 activates the emergency module 156, which isdescribed in greater detail below.

As illustrated in FIG. 3, the user 112 may also engage a selectablebutton or selectable icon 310 presented to the user 112 on a dashboard304. In various examples, the dashboard 304 allows the user 112 on theuser device 102 to see and access data stored on the safety server 104.In the present example, the dashboard 304 includes four selectable icons310 a,b,c,d; however, in various other examples, the dashboard 304 mayinclude any desired number of selectable icons 310. The selectable icons310 may be associated with various user data stored on the safety server104 such as historical BAC levels, previous incidents, services used,heroes alerted and hero responses, current alerts, prior alerts, andvarious other data gathered by the safety mobile application such thatthe user 112 is presented with particular user data upon selection of aselectable icon 310. The selectable icons 310 may also be associatedwith various features of the safety mobile application such as a helpfeature, a settings feature, a pairing feature on the measuring device120, and various other similar features that may be utilized by the user112.

In various examples, the user 112 may also engage the dashboard 304 todefine what alerts are monitored and sent by the safety mobileapplication to approved heros 106 from the user device 102 via thesafety server 104. In various examples, the user 112 may define whatalerts are monitored and sent by engaging a “Settings” selectable icon310. In various examples, an approved source may also define rules andalerts for the safety mobile application. The approved source may beselected from the group including, but not limited to, parent, legalguardian, employer, friend, relative, government source, or any othersource approved by the user 112 and/or provided access credentials basedon the source meeting certain approval criteria. In various examples,these defined rules may include those from the group including, but notlimited to, BAC levels, emergency panic levels, parent-based rules,employer-based rules, and any other similar rules defining variousthresholds at which alerts are monitored and sent by the user device 102via the safety server 104. In various examples, these rules are storedon the safety server 104.

As illustrated in FIG. 3, the safety mobile application displays on thehome screen interface instructions or steps 302 the user 112 may take toactivate the BAC monitoring module 154. In the present example, thesafety mobile application presents three steps 302 a,b,c to the user 112on the home screen interface; however, the number of steps 302 shouldnot be considered limiting on the current disclosure. In variousexamples, the steps 302 may include instructions such as how to turn onthe monitoring device, how to begin testing, how long to use themonitoring device, how to view the results, and various otherinstructions.

FIGS. 4-11 illustrate examples of user interfaces400,500,600,700,800,900,1000,1100 on the user device 102 operated by theuser 112 upon activation of the BAC monitoring module 154 from the homescreen interface illustrated in FIG. 3. In various examples, the BACmonitoring module 154 registers and records the user's 112 BAC levels asstored data. The BAC monitoring module 154 includes associateddisclaimers on accuracy of data which the user 112 agrees to in FIG. 2.

Similar to FIGS. 2 and 3, the labels and placement of interface elementsare representative only and that the importance is on their underlyingfunctions. Likewise, it should be understood that any buttons can bephysically moveable switches, softkeys, proximity switches, voicedetectors, motion sensor, etc. operable to perform a function inresponse to user's 112 desires.

In various examples, the BAC monitoring module 154 is activated by theuser 112 activating the measuring device 120 such that the measuringdevice 120 is in wireless communication with the user device 102. Invarious examples, the measuring device 120 is a breathalyzer devicewhich connects to the user device 102 via Bluetooth or using anothersuitable wired or wireless technology. In various examples, themeasuring device 120 includes a status indicator, such as a status bar,display, or various other indicators, such that the user 112 using themeasuring device 120 is notified when a measuring of user data iscompleted. In various other examples, the status indicator may also bedisplayed on a user interface of the user device 102.

After the measuring device 120 is turned on and connected to the userdevice 102, the safety mobile application starts a timer for themeasuring period. The measuring period corresponds with the amount oftime that is needed by the measuring device 120 to collect the user datafrom the user 112. In various examples, the measuring period is apredetermined period of time. In various examples, the measuring periodmay be between zero and fifteen seconds, such as about three to sevenseconds, such as about three to five seconds. In various other examples,the measuring period may be any suitable time period corresponding withthe amount of time needed by the measuring device 120 to collect userdata. For example, in various other examples, the measuring period maybe less than three seconds, greater than 15 seconds, or any othersuitable time interval. As illustrated in FIG. 4, upon initiation of themeasuring period, the BAC monitoring module 154 activates a camera 208of the user device 102 and records a video 402 of the user 112 using themeasuring device 120 via the camera 208. In various examples, themeasuring period is one of a plurality of measuring periods.

In various examples, the BAC monitoring module 154 may prompt the user112 to utilize the measuring device 120 to begin the measuring period.For example, when the measuring device 120 is the breathalyzer device,the BAC monitoring module 154 may prompt the user 112 to blow into thebreathalyzer device and begin the measuring period. In various examples,the measuring device 120 may transmit the user data to the user device102 during the measuring period or after the conclusion of the measuringperiod.

FIG. 4 illustrates the user interface 400. As illustrated in FIG. 4 andas previously described, in various examples, the BAC monitoring module154 records a video 402 of the user 112 while the user 112 is using themeasuring device 120 for the duration of the measuring period. Invarious examples, the BAC monitoring module 154 further takes a pictureof the user 112 using the measuring device 120 via the camera 208. Invarious examples, the BAC monitoring module 154 may take a series ofpictures at predetermined time intervals during the measuring period. Invarious examples, the duration of the video 402 is about the same as theduration of the measuring period; however, in various other examples,the duration of the video 402 may be less than the duration of themeasuring period. For example, the duration of the video 402 may bebetween zero and fifteen seconds, such as about three to seven seconds,such as about three to five seconds. In various other examples, theduration of the video 402 may be less than about three seconds orgreater than about fifteen seconds. As illustrated in FIG. 4, the user112 may engage a cancel element 404. Engagement with the cancel element404 may cause the safety mobile application to stop the measuringperiod, stop recording the video 402, and exit the BAC monitoring module154.

A common problem with user devices 102 such as portable computers,mobile phones, wearable computers, laptops, smart phones, tablets, andother similar mobile devices is that these devices areresource-constrained inherent in the mobile device design. Theresource-constrained nature of mobile devices makes it difficult for themobile devices to support computation-intensive applications whilemaintaining quality. In many circumstances, running one or morecomputation-intensive applications on a mobile device causes a reductionin functionality and disrupts or slows down the speed and effectivenessat which the application or applications run. Video processing by theuser device 102 and wireless control of and communication with themeasuring device 120 by the user device 102, as supported by the safetymobile application, are both computation-intensive andresource-intensive processes for the user device 102 to run. By limitingthe duration of the video 402 to a relatively short time frame, thesafety mobile application ensures that the user device 102 is able tosupport both the video processing and safety device communicationwithout compromising the functionality or speed at which either processoperates.

The video-recording feature of the safety mobile application in the BACmonitoring module 154 also keeps a user 112 from switching users orforging results during the measuring period of the BAC monitoring module154 because the BAC monitoring module 154 time and date stamps the video402, as described in greater detail below, which is sent to the hero 114with the corresponding result from the measuring period (illustrated inFIG. 7). Once the measuring period is completed, the BAC monitoringmodule 154 may also time and date stamp the video 402 and/or picture andtransmit this data from the user device 102 to the safety server 104.The BAC monitoring module 154 further time and date stamps the testingresults for the user 112 for the measuring period and transmits thisdata from the user device 102 to the safety server 104. In variousexamples, the BAC monitoring module 154 may further store locationinformation for the user data indicating the location of the user 112when the user data was obtained. The BAC monitoring module 154 maydetermine whether the testing results violate or meet any rulespreviously defined by the user 112 and stored on the safety server 104as described above. In various examples, if a rule is violated or met,the BAC monitoring module 154 automatically sends a message to the hero114 or other contact, as described below.

FIG. 5 illustrates the user interface 500 on the user device 102provided by the BAC monitoring module 154 upon completion by the user112 of the measuring period. As illustrated in FIG. 5, the BACmonitoring module 154 displays a testing result element 502 presentingthe testing results 604 for the user 112 from the measuring period. Invarious examples, the BAC monitoring module 154 may compare the testingresults 604 to the predefined rules for any user data. In variousexamples, if the testing results 604 violate a predefined rule, the BACmonitoring module 154 may display the testing results 604 in a firstcolor in the testing result element 502, and if the testing results 604do not violate the predefined rule, the BAC monitoring module 154 maydisplay the testing results 604 in a second color in the testing resultelement 502.

As illustrated in FIG. 5, the user 112 may engage with a hero requestelement 504, which is described in greater detail below. The user 112may also engage with a dashboard 506, which may be functionally similarto the dashboard 304, and include selectable icons 508 a,b,c,d orbuttons, which may be functionally similar to the selectable icons 310.As illustrated in FIG. 5, in various examples, the user 112 may furtherengage with service provider elements 510 a,b,c, which correspond withthe service providers 110 a,b,c, respectively, and may be selected toaccess various information or services provided by the service providers110 a,b,c as described in greater detail below. In various examples, theinformation or services provided by the service providers 110 a,b,c mayalso be accessed through one of the selectable icons 310 on thedashboard 304 or one of the selectable icons 508 on the dashboard 506.

The hero request element 504 is selectable to enable the user 112 tocommunicate data to the preselected hero 114 or various other contactsif the user 112 desires to have assistance from the hero 114. In variousexamples, the hero request element 504 is an optional selectable featurefor the user 112 to select on the user device 102 after the measuringperiod of the BAC monitoring module 154 is completed. In variousexamples, the hero request element 504, as an optional selectablefeature, allows the user 112 to determine when to communicate thatassistance is needed by the user 112 to the hero 106. In variousexamples, the hero 106 may be the hero's device or another contact'sdevice.

In various examples, the safety mobile application automaticallycommunicates a status report message 602 to a preselected hero 114 afterthe measuring period is completed. As described above, in variousexamples, the safety server 104 determines whether the testing results604 violate or meet any rules defined for the user 112. If a rule is metor violated, depending on the rule, the safety server 104 maycommunicate this violation or compliance to the user device 102, causingthe safety mobile application to automatically send the message to thehero's hero 106 from the user device 102. By way of example, in variousexamples where the measuring device 120 is a breathalyzer device, theapplication may automatically send a message to a contact if the safetyserver 104 determines the user's BAC is above the legal driving limit.

FIG. 6 illustrates one example of the status report message 602automatically sent by the safety mobile application from the user device102 to a hero 106 after the termination of the measuring period on theuser interface 600. In various examples, the content of the statusreport message 602 is automatically generated by the BAC monitoringmodule 154; however, in various other examples, the content of thestatus report message 602 is customizable by the user 112. Asillustrated in FIG. 6, in various examples, the content of the statusreport message 602 includes the testing results 604 of the user 112 fromthe measuring period. In various examples, the status report message 602also includes identifying information to identify the testing results604 as a particular testing result. The identifying information mayinclude a time stamp 606 and a date stamp 608. The identifyinginformation may also include location information 610 of the user device102. In various examples, the BAC monitoring module 154 obtains thelocation information 610 of the user device 102 through a form of GPS(Global Positioning System) functionality on the user device 102. Asillustrated in FIG. 6, in various examples, the message includes thelocation information 610 of the user device 102. In various examples,the location information 610 can be coordinates of the user device 102.In various examples, the location information 610 includes a link to amapping or location based service or application such as Google Maps,Bing Maps, MapQuest, and other similar mapping applications which candisplay the GPS coordinates and location of the user device 102 on amap. The hero 114 may use the location information 610 to go to thelocation of the user device 102 if desired by the hero 114.

As described previously, the BAC monitoring module 154 may mark orotherwise store the identifying information with the testing results 604and the video 402 after the conclusion of the measuring period. Invarious other examples, the BAC monitoring module 154 may includevarious other identifying information in addition to or in place of anyof the time stamp 606, date stamp 608, or location information 610 thatmay be used to identify the testing results 604 as a particular testingresult. The identifying information, such as the time stamp 606 and datestamp 608, is utilized by the safety mobile application to create a userhistory is various examples. The user history may be stored on thesafety server 104 in various examples.

As illustrated in FIG. 6, in various examples, the status report message602 may further include the video 402 of the user 112 using themeasuring device 120 during the measuring period. The video 402 includedin the status report message 602 is provided as verification for thehero 114 on the hero 106 that the testing results 604 in the statusreport message 602 are the results of the specific user 112. In thismanner, the video 402 prevents a user 112 from switching users orforging results during the BAC monitoring module 154 because the safetymobile application matches the time and date stamped video 402 with thecorresponding time and date stamped testing results 604 and sends thevideo 402 and testing results 604 in the status report message 602. Thevideo 402 included as part of the status report message 602 may beutilized to verify that the testing results 604 were obtained from theuser 112 and not from another person As illustrated in FIG. 6, the BACmonitoring module 154 may further provide customizable textingfunctionality 612 that the user 112 may engage to create a customizedmessage to the hero 114 in addition to the testing results 604 andidentifying information for the testing results 604.

In various examples, the BAC monitoring module 154 may communicate thetesting results 604 for the user 112 from the measuring period and anindication of whether the testing results 604 are below or above apredetermined threshold to a third party safety device such as a carignition interlock device. In various examples where the hero 106 isincluded, the user device 102 may be in wireless communication with thehero 106. In various examples, the rules or predefined user datathreshold may be provided by the operator or provider of the hero 106.For example, when the third party safety device is the car ignitioninterlock, the provider of the car ignition interlock or the entityusing the car ignition interlock may predefine various user datathresholds. In these examples, the BAC monitoring module 154 may comparethe user data to the user data thresholds and compare the results to thethird party safety device. For example, when the third party safetydevice is the car ignition interlock and the measuring device 120 is abreathalyzer, the BAC monitoring module 154 may compare the user datawith the threshold at which the car ignition interlock will prevent acar's engine from being started. Depending on the result of thecomparison, the BAC monitoring module 154 may communicate with the carignition interlock that the user data is below the threshold, therebyenabling the car engine to start, or that the user data is above thethreshold, thereby preventing the car engine from starting.

FIG. 7 illustrates an example of a hero request message 702 created bythe hero request element 504 of the safety mobile application via theuser interface 700. Similar to the status report message 602, in variousexamples, at least a portion of the content of the hero request message702 may be automatically generated by the safety mobile application Invarious examples as illustrated in FIG. 7, the content of the herorequest message 702 automatically generated by the safety mobileapplication may include the testing results 604 and a request by theuser 112 for assistance from the hero 114. The hero request message 702may include the location information 610 of the user device 102. Theautomatically generated content of the hero request message 702 may alsoinclude a location link 710 to a mapping or location based service orapplication which can display the GPS coordinates and location of theuser device 102 on a map.

As illustrated in FIG. 7, the automatically generated content of thehero request message 702 also includes a picture 704 of the user 112using the measuring device 120 in various examples. Similar to how theBAC monitoring module 154 utilized the camera 208 to record a video 402of the user 112 during the measuring period, in various examples, theBAC monitoring module 154 may utilized the camera 208 to take a picture704 of the user 112 during the measuring period. The BAC monitoringmodule 154 may then store the picture 704 with identifying information,such as a time stamp 606 and a date stamp 608, on the safety server 104.When the hero request message 702 is generated by the safety mobileapplication, the safety mobile application matches the time and datestamped picture 704 with the corresponding testing results 604 and sendsthe picture 704 and testing results 604 in the hero request message 702.As illustrated in FIG. 7, the safety mobile application may furtherprovide customizable texting functionality 712, which is similar to thetexting functionality 612, that the user 112 may engage to create acustomized message to the hero 114 in addition to the testing results604 and identifying information for the testing results 604. In variousother examples, the hero request message 702 may include the video 402.

Referring back to FIG. 5, in various examples, the service providerelement 510 a is a taxi service element, service provider element 510 bis a hotel service element, and service provider element 510 c is adriver-for-hire provider element. In general, selection of any of theservice provider elements 510 enables the user 112 to view and selectvarious resources to alert or receive services from. In variousexamples, these resources may include those from the group including,but not limited to, counseling, food, lodging, transportation, employer,government services, aid, or any other resources the user 112 may wantto alert or receive services from. In various examples, the list ofresources presented upon the selection of each service provider element510 a,b,c is preselected by the user 112 as approved trusted resources.These approved selected resources may be stored on the safety server 104and associated with that particular user 112. In various examples, thelist of resources presented upon the selection of each service providerelement 510 a,b,c is based on location based services within ageographic region associated with the user device 102. In theseexamples, the GPS functionality of the user device 102 may be used tolocate the user device 102 such that the safety mobile application maydetermine nearby resources via the service provider elements 510 a,b,c.In various examples, the services of the service providers as displayedon the user device 102 as service provider elements 510 a,b,c may besorted or prioritized by the safety mobile application based onaffiliations, promotions, sponsorships, discounts, services, or variousother categorical criteria.

In various examples, after the user 112 selects one of the listedresources or services provided by one of the service providers, thesafety mobile application may put the user 112 in communication with theresource via the user device 102, provide contact information for theresource for the user 112 to selectably communicate with the resourcevia the user device 102, or provide walking directions for the user 112to the resource. In various other examples, the safety mobileapplication may provide various other information corresponding to theresource selected by the user 112.

FIGS. 8 and 9 illustrate user interfaces 800,900 upon the selection bythe user 112 of a hotel service element, such as the service providerelement 510 b. As illustrated in FIGS. 8 and 9, in various examples, theservice provider elements 510 a,c may be presented for the user 112 toselect as desired. In various examples, the user interface furtherprovides additional service provider elements 510 for the user 112 toselect, such as service provider element 510 d. In present example, theservice provider element 510 d is a legal services element; however, thetype of service provider element should not be considered limiting onthe current disclosure. The number of service provider elements 510should not be considered limiting on the current disclosure.

As illustrated, the user interface includes a listing of serviceresources, such as a listing of hotels 802 a-j with distances 804 a-jand direction elements 806 a-j to each hotel 802 a-j, respectively. Invarious examples, the direction elements 806 a-j are selectable linkssuch that selection of a direction element 806, such as directionelement 806 a, provides the user 112 with the user interface 1000 havinga map 1002 via a mapping or location based service or application, asillustrated in FIG. 10, which can display the GPS coordinates andlocation of the user device 1006 and the GPS coordinates and location ofthe hotel 802 a corresponding with the direction element 806 a selected,along with directions 1004 from the user device 1006 to the hotel 802 a.

FIG. 11 illustrates the user interface 1100 on the user device 102 uponthe selection by the user 112 of the service provider element 510 d.Similar to the user interface illustrated in FIGS. 8 and 9, the userinterface illustrated in FIG. 11 includes a list of service resources.In the present example, the listing of service resources includes alisting of legal services 1102 a-e and communication elements 1104 a-efor each legal service 1102 a-e, respectively.

FIGS. 12-16 illustrate one example of a sequence of user interfaces1200,1300,1400,1500,1600 on the user device 102 operated by the user 112upon activation of the emergency module 156 from the home screeninterface illustrated in FIG. 3. Similar to FIGS. 2 and 3, the labelsand placement of interface elements are representative only and that theimportance is on their underlying functions. Likewise, it should beunderstood that any buttons can be physically moveable switches,softkeys, proximity switches, voice detectors, motion sensor, etc.operable to perform a function in response to user's 112 desires.

In various examples, the emergency module 156 is activated uponselection of the panic element 308 by the user 112. After the emergencymodule 156 is activated, the emergency module 156 may present or displaya confirmation indication or message 1202 on the user interface. Invarious examples, the confirmation message 1202 provides confirmationthat that emergency module 156 has been activated and that the hero 114has been contacted. The confirmation message 1202 provides aconfirmation of a receipt of the indication of the emergency situationfrom the user 112.

In various examples, upon activation of the emergency module 156, theemergency module 156 starts a timer for an emergency period. Theemergency module 156 may automatically begin video and audio recordingof the situation as viewed through the camera 208 and as heard through amicrophone (not illustrated) of the user device 102. FIG. 13 illustratesone example of a safety video 1302 being recorded automatically uponselection of the panic element 308. Safety video 1302 may be similar tovideo 402 and have a relatively short duration. For example, in variousexamples, the safety video 1302 may be recorded by the emergency module156 via the camera 208 for a duration between zero and fifteen seconds,such as about three to seven seconds, such as about three to fiveseconds. In various other examples, the video and audio recording periodmay be any suitable time period. In various examples, the audio andvideo recording records a situation in progress or after the event hasoccurred to validate the situation underway and capture as many factsand data available. As with other data collected by the safety mobileapplication, the emergency module 156 marks the data captured in thesafety video 1302 and audio recording with identifying information asdescribed above, such as time and date information, and transmits thedata to the safety server 104 from the user device 102 for securestorage. In various examples, the data is secured on the safety server104 through various security protocols including, but not limited to,passcodes, facial recognition, fingerprint scans, and various othersecurity protocols for securely storing the data on the safety server104. In various examples, storage of data on the safety server 104prevents the data from being destroyed even if removed from the userdevice 102. As illustrated in FIG. 13, the user 112 may engage a cancelelement 1304, which may be functionally similar to cancel element 404.Engagement with the cancel element 1304 may cause the safety mobileapplication to exit the emergency module 156. In addition toautomatically starting video and audio recording, after the panicelement 308 is selected, the emergency module 156 sends an automaticmessage to at least one contact, such as the hero 114.

One example of an automatic alert message 1402 sent to at least onecontact is illustrated in FIG. 14. In various examples, the alertmessage 1402 includes an alert notification 1404 indicating that theuser 112 has selected the panic element 308. The alert message 1402 mayalso provide location information 610 of the user device 102. In variousexamples, the content of the alert message 1402 is automaticallygenerated by the emergency module 156. In various examples, multiplealert notifications 1404 are included in the alert message 1402. Invarious examples, new alert notifications 1404 are sent as the locationinformation 610 of the user device 102 changes. As illustrated in FIG.14, the emergency module 156 may further provide customizable textingfunctionality 1406 that the user 112 may engage to create a customizedmessage to the hero 114. The texting functionality 1406 is similar tothe texting functionalities 612,712, respectively.

FIG. 15 illustrates another example of an alert message 1502 created bythe emergency module 156 upon selection of the panic element 308. Invarious examples, the content of the alert message 1502 is automaticallygenerated by the emergency module 156. As illustrated in FIG. 15, invarious examples, the alert message 1502 is similar to alert message1402 and includes an alert notification 1404. In various examples,multiple alert notifications 1404 are included in the alert message1502. As illustrated in FIG. 15, in various examples, the alert message1502 also includes location information 610 of the user device 102. Invarious examples, new alert notifications 1404 are created and newlocation information 610 is included in the alert message 1502 as thelocation information 610 of the user device 102 changes. As illustratedin FIG. 15, in various examples, the alert message 1502 also includesthe safety video 1302 recorded by the emergency module 156. Asillustrated in FIG. 15, in various examples, multiple safety videos 1302may be included in the alert message 1502. In various examples, a newsafety video 1302 is included in the alert message 1502 when the panicelement 308 is pressed.

As previously described, in various examples, the emergency module 156starts the timer for the emergency period after the panic element 308 isselected by the user 112. In various examples, after the emergencyperiod has expired, the safety server 104 communicates a follow-upmessage 1602 to the user device 102 as illustrated in FIG. 16. Thefollow-up message 1602 may confirm that the emergency module 156 wasactivated. The follow-up message 1602 may also prompt the user 112 toindicate if the emergency situation was addressed in various examples.In various examples, the follow-up message 1602 may provide the user 112with a link 1604 to additional resources to address the emergencysituation. In various examples, the emergency period is about 24 hoursafter the panic element 308 was selected. In various examples, theemergency module 156 may determine whether additional follow-up with theuser 112 is needed based on the response to the follow-up message 1602.

FIGS. 17-19 illustrate examples of user interfaces 1700,1800,1900 on theuser device 102 operated by the user 112 upon activation of the BACmonitoring module 154 from the home screen interface illustrated in FIG.3 in systems where the safety mobile application utilizes the twomeasuring devices 120 a,b illustrated in FIG. 1B. In the presentexample, the first measuring device 120 a is a breathalyzer configuredto measure a user's BAC and the second measuring device 120 b is a heartrate monitor configured to measure a heart rate of the user 112; howeverthe disclosure of the breathalyzer and heart rate monitor should not beconsidered limiting on the current disclosure as the measuring devices120 a,b may be any desirable type of measuring device. Similar to FIGS.2 and 3, the labels and placement of interface elements arerepresentative only and that the importance is on their underlyingfunctions. Likewise, it should be understood that any buttons can bephysically moveable switches, softkeys, proximity switches, voicedetectors, motion sensor, etc. operable to perform a function inresponse to user's desires.

In various examples, if the BAC monitoring module 154 determines thatthe first type of user data received from the first measuring device 120a during a first measuring period is below or above a predeterminedthreshold for the first type of user data, the BAC monitoring module 154may initiate a second measuring period during with the second measuringdevice 120 b to monitor the second type of user data. By way of example,if the BAC monitoring module 154 determines that the BAC of the user 112is above a predefined threshold, the BAC monitoring module 154 initiatesa second measuring period during which the heart rate of the user 112 ismonitored.

Upon completion of the second measuring period, the BAC monitoringmodule 154 determines whether the second type of user data is below orabove a predetermined threshold for the second type of user data.Depending on the type of data and the threshold for that data, the BACmonitoring module 154 may automatically transmit a message to the hero114. The alert message to the hero 114 may include the results of thefirst type of user data and the results of the second type of user data,as described in greater detail below.

FIG. 17 illustrates the user interface 1700 a presented to the user 112on the user device 102 after the BAC monitoring module 154 haddetermined that the first type of user data was below or above apredetermined threshold for the first type of user data and after theconclusion of a second measuring period. As illustrated in FIG. 17, theuser interface 1700 may include an average 1702 of the second type ofuser data and various other levels 1704,1706 of the second type of userdata. FIG. 18 illustrates the user interface 1800 including an average1802 of the second type of user data and various other levels 1804,1806of the second type of user data.

FIG. 19 illustrates an alert message 1902 automatically generated by theBAC monitoring module 154 and sent from the user device 102 to the hero106. In various examples, the alert message 1902 is automaticallygenerated after the BAC monitoring module 154 determines that the firsttype of user data is above or below a predetermined threshold for thefirst type of user data and that the second type of user data is aboveor below a predetermined threshold for the second type of user data. Invarious examples, the content of the alert message 1902 is automaticallygenerated by the BAC monitoring module 154; however, in various otherexamples, the content of the alert message 1902 is customizable by theuser 112.

As illustrated in FIG. 19, in various examples, the content of the alertmessage 1902 includes an indication 1904 that assistance is needed bythe user 112 because the two types of user data are above or below thepredefined thresholds, respectively. In various examples, the alertmessage 1902 also includes identifying information similar to thatdescribed above. As illustrated in FIG. 19, in various examples, themessage includes the location information 610 of the user device 102. Asillustrated in FIG. 19, the BAC monitoring module 154 may furtherprovide customizable texting functionality 1906 that the user 112 mayengage to create a customized message to the hero 114.

In various other examples, the BAC monitoring module 154 willconcurrently receive the first type and second type of user data asmeasured during a measuring period. In these examples, the status reportmessages 602 may include the first type and the second type of user dataas measured during the measuring period. In various examples, an alertmessage similar to the alert message 1902 may be generated if either thefirst type of user data is below or above the predetermined thresholdfor the first type of user data or the second type of user data is belowor above the predetermined threshold for the second type of user data.

FIG. 20 illustrates an example of a method 2000 for monitoring a safetycondition of a user 112 with a safety mobile application. The method2000 is performable and executable on a computing device such as thosedescribed above with reference to FIG. 1. It should be noted that any ofthe steps of any of the methods described herein may be performed in anyorder or could be performed in sub-steps that are done in any order orthat are separated in time from each other by other steps or sub-steps,and the disclosure of a particular order of steps should not beconsidered limiting on the current disclosure. In various examples, themethod 2000 is implemented by the BAC monitoring module 154.

In various examples, at step 2002, the method 2000 includes instructingthe user 112 to start using the measuring device 120. In variousexamples, instructing the user 112 to start using the measuring device120 includes enabling the user 112 to begin a measuring period with themeasuring device 120. In various examples, prior to step 2002, themethod 2000 may include enabling the user 112 to log in to the mobilesafety application on the user device 102. In various examples, prior tostep 2002, the method 2000 may also include enabling the user 112 toselect or input a hero 114 with the mobile safety application. At step2004, in various examples, the method 2000 includes starting a measuringperiod. In step 2006, the method 2000 includes starting a multimediaactivity. In various examples, starting the multimedia activity may beselected from the group including starting to record the video 402 ofthe user 112 using the user device 102, taking pictures of the user 112using the user device 102, recording an audio recording of the user 112using the user device 102, and various other similar activities.

In step 2008, it is determined whether the measuring period has expired.If the measuring period has not expired, the method 2000 continues tostep 2010 where recording of the video 402 of the user 112 using themeasuring device 120 continues. If the measuring period has expired instep 2008, in step 2012, the method 2000 includes receiving user dataabout the user 112 using the measuring device 120 during the measuringperiod from the measuring device 120. In step 2014, the method 2000includes marking and providing identifying information for the user dataand sending the user data to the safety server 104. In various examples,the method 2000 at step 2014 further includes providing the video 402 ofthe user 112 during the measuring period with identifying informationand sending the video 402 to the safety server 104. In step 2016, themethod 2000 includes sending a status report to the hero 114. The statusreport includes at least the user data and accompanying identifyinginformation. In various examples, the method 2000 at step 2016 furtherincludes sending the video 402 of the user 112 to the hero 106. Invarious examples, in step 2016, the message may further include an audiorecording of the user 112 from the measuring period, a picture 704 ofthe user 112 from the measuring period, location information 610 of theuser device 102, or any other identifying information as describedabove.

FIG. 21 illustrates another example of a method 2100 for monitoring asafety condition of a user 112 with a safety mobile application. Themethod 2100 is performable and executable on a computing device such asthose described above with reference to FIG. 1. It should be noted thatany of the steps of any of the methods described herein may be performedin any order or could be performed in sub-steps that are done in anyorder or that are separated in time from each other by other steps orsub-steps, and the disclosure of a particular order of steps should notbe considered limiting on the current disclosure. In various examples,the method 2100 is implemented by the emergency module 156.

In various examples, at step 2102, the method 2100 includes receivingfrom a user 112 an indication of an emergency situation. In variousexamples, as described above, the safety mobile application receives anindication of an emergency situation when the user 112 selects the panicelement 308. In various examples, prior to step 2102, the method 2100may include enabling the user 112 to log in to the safety mobileapplication on the user device 102. In various examples, prior to step2102, the method 2100 may also include enabling the user 112 to selector input a hero 114 with the safety mobile application. At step 2104, invarious examples, the method 2100 includes starting an internal clockfor an emergency time period. In step 2106, the method 2100 includesrecording the safety video 1302 of the user 112 in the emergencysituation after receiving the indication of the emergency situation. Invarious other examples, at step 2106, the method 2100 further includesrecording an audio recording and/or a picture 704 of the user 112 in theemergency situation. At step 2108, the method 2100 includes determiningthe geolocation of the user device 102 after receiving the indication ofthe emergency situation. At step 2110, in various examples, the method2100 includes communicating an alert message 1502 to the hero 114. Thealert message 1502 includes the geolocation of the user device 102 andthe safety video 1302 of the user 112 to the hero 106. In variousexamples, at step 2110, the message may further include an audiorecording of the user 112 in the emergency situation, a picture 704 ofthe user 112 in the emergency situation, or any other information asdescribed above.

In step 2112, it is determined whether another indication of anemergency situation has been received from the user 112. If anotherindication of an emergency situation has been received from the user112, the method 2100 returns to step 2106. If another indication of anemergency situation has not been received, in step 2114 it is determinedwhether the location of the user device 102 has changed. If the locationof the user device 102 has changed, the method 2100 returns to step2106. If the location of the user device 102 has not changed, in step2116 it is determined whether the emergency period has ended. If theemergency period has not ended, the method 2100 returns to step 2112. Ifthe emergency period has ended, in step 2118 the method 2100 includessending a follow-up message 1602 to the user device 102.

In various examples, the safety mobile application may utilize inputfrom multiple measuring devices 120 a,b, as illustrated for example inFIG. 1B. In these examples, each measuring device 120 a,b may measure adifferent type of user data during the measuring period. For example,the first measuring device 120 a may measure a first type of user dataduring the measuring period and the second measuring device 120 b maymeasure a second type of user data during the measuring period.

One should note that conditional language, such as, among others, “can,”“could,” “might,” or “may,” unless specifically stated otherwise, orotherwise understood within the context as used, is generally intendedto convey that certain examples include, while other examples do notinclude, certain features, elements and/or steps. Thus, such conditionallanguage is not generally intended to imply that features, elementsand/or steps are in any way required for one or more particular examplesor that one or more particular examples necessarily include logic fordeciding, with or without user input or prompting, whether thesefeatures, elements and/or steps are included or are to be performed inany particular example.

It should be emphasized that the above-described examples are merelypossible examples of implementations, merely set forth for a clearunderstanding of the principles of the present disclosure. Any processdescriptions or blocks in flow diagrams should be understood asrepresenting modules, segments, algorithms, or portions of code whichinclude one or more executable instructions for implementing specificlogical functions or steps in the process, and alternate implementationsare included in which functions may not be included or executed at all,may be executed out of order from that illustrated or discussed,including substantially concurrently or in reverse order, depending onthe functionality involved, as would be understood by those reasonablyskilled in the art of the present disclosure. Many variations andmodifications may be made to the above-described example(s) withoutdeparting substantially from the spirit and principles of the presentdisclosure. Further, the scope of the present disclosure is intended tocover any and all combinations and sub-combinations of all elements,features, and aspects discussed above. All such modifications andvariations are intended to be included herein within the scope of thepresent disclosure, and all possible claims to individual aspects orcombinations of elements or steps are intended to be supported by thepresent disclosure.

That which is claimed is:
 1. A system for monitoring a safety conditionof a user, the system comprising: a hero device associated with a hero;and a mobile device associated with the user, the mobile devicecomprising a processor and a memory device, the memory device configuredto store a safety mobile application enabling the mobile device to:receive, from the user, an indication of an emergency situation, recorda video of the user in the emergency situation, determine a geolocationof the mobile device, and communicate to the hero device a messagecomprising the video of the user in the emergency situation and thegeolocation of the mobile device, wherein the recording of the video,the determining of the geolocation, and the communicating of the messageare automatically activated in succession following the indication ofthe emergency situation by the user, wherein the safety mobileapplication further enables the mobile device to determine whether afirst type of user data is above a first predetermined threshold anddetermine whether a second type of user data is above a secondpredetermined threshold.
 2. The system of claim 1, wherein the messageis a first message, and wherein the safety mobile application furtherenables the mobile device to: determine whether the geolocation of themobile device has changed to a new geolocation; and communicate to thehero device a second message having the new geolocation of the mobiledevice.
 3. The system of claim 1, wherein the video is a first video andthe message is a first message, and wherein the safety mobileapplication further enables the mobile device to: record a second videoof the user in the emergency situation; and communicate to the herodevice a second message comprising the second video.
 4. The system ofclaim 1, wherein the safety mobile application further enables themobile device to record an audio recording of the user in the emergencysituation.
 5. The system of claim 1, further comprising a safety server,wherein the safety server is configured to receive, from the mobiledevice, the video of the user in the emergency situation and to securelystore the video of the user in the emergency situation.
 6. The system ofclaim 1, wherein the hero device is associated with a predeterminedcontact selectable on the mobile device.
 7. The system of claim 1,wherein the safety mobile application further enables the mobile deviceto display confirmation of a receipt of the indication of the emergencysituation.
 8. A method of monitoring a safety condition of a user, themethod comprising: receiving from the user an indication of an emergencysituation; recording a video of the user in the emergency situation;determining a geolocation of a mobile device associated with the user;and communicating a message to a hero device, the message comprising thevideo of the user in the emergency situation and the geolocation of themobile device, the hero device associated with a hero, wherein therecording of the video, the determining of the geolocation, and thecommunicating of the message are automatically engaged in succession byan emergency module on the mobile device, the emergency module on themobile device configured to determine whether a first type of user datais above a first predetermined threshold and determine whether a secondtype of user data is above a second predetermined threshold.
 9. Themethod of claim 8, further comprising: determining whether thegeolocation of the mobile device has changed to a new geolocation; andcommunicating to the hero device a second message having the newgeolocation of the mobile device.
 10. The method of claim 8, wherein thevideo is a first video and the message is a first message, the methodfurther comprising: recording a second video of the user in theemergency situation; and communicating to the hero device a secondmessage comprising the second video.
 11. The method of claim 8, furthercomprising: starting an emergency period timer upon receiving from theuser the indication of the emergency situation; monitoring the emergencyperiod timer; and transmitting a follow-up message to the mobile deviceupon expiration of the emergency period timer.
 12. The method of claim8, further comprising recording an audio recording of the user in theemergency situation.